Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update conda to use Python 3.12, drop 3.9 and 3.10 #39164

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

tobiasdiez
Copy link
Contributor

In line with Spec 0, we drop Python 3.9 and 3.10 support (in this PR only for conda). Instead Python 3.11 and 3.12 is used for the CI.

(Python 3.13 still needs a few package updates in the conda universe #39163)

📝 Checklist

  • The title is concise and informative.
  • The description explains in detail what this PR is about.
  • I have linked a relevant issue or discussion.
  • I have created tests covering the changes.
  • I have updated the documentation and checked the documentation preview.

⌛ Dependencies

Copy link

github-actions bot commented Dec 19, 2024

Documentation preview for this PR (built with commit 9ea715f; changes) is ready! 🎉
This preview will update shortly after each push to this PR.

@tobiasdiez tobiasdiez marked this pull request as ready for review December 19, 2024 05:35
@tobiasdiez tobiasdiez requested a review from dimpase December 23, 2024 04:39
@tobiasdiez
Copy link
Contributor Author

@dimpase could you please have a look? (It's already tested by ci and automatically generated, so no need to run it locally I think)

@dimpase
Copy link
Member

dimpase commented Jan 3, 2025

Please drop the CI for 3.9, too - I still see

Conda (ubuntu-latest, 3.9, environment) Expected — Waiting for status to be reported

@tobiasdiez
Copy link
Contributor Author

Please drop the CI for 3.9, too - I still see

Conda (ubuntu-latest, 3.9, environment) Expected — Waiting for status to be reported

It's already dropped. The message is saying that it expects an status report but haven't received one. This can be fixed, once this PR is merged, by changing the branch protection rules (need to be done by an admin under https://github.com/sagemath/sage/settings/branches)

Copy link
Member

@dimpase dimpase left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@tobiasdiez
Copy link
Contributor Author

lgtm

Thanks!

@tobiasdiez tobiasdiez mentioned this pull request Jan 4, 2025
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants